Radio link failure handling for dual connectivity

ABSTRACT

Embodiments of an evolved Node B (eNB) and methods for radio link failure handling for dual connectivity are generally described herein. A method performed by circuitry of a User Equipment (UE) may include connecting, at a UE, to a Master eNB (MeNB) and connecting to a Secondary eNB (SeNB). The method may include determining, at the UE, that one of the connections has a Radio Link Failure and determining at the UE, that the other of the connections remains connected to the UE. The method may include refraining from initiating a Radio Resource Control (RRC) re-establishment procedure while at least one of the connections does not have a radio link failure.

CLAIM OF PRIORITY

This patent application is a continuation of U.S. patent applicationSer. No. 14/491,639, filed Sep. 19, 2014, which claims the benefit ofpriority of U.S. Provisional Patent Application Ser. No. 61/898,425,entitled “Advanced Wireless Communication Systems and Techniques,” filedon Oct. 31, 2013, each of which are hereby incorporated by referenceherein in their entirety.

BACKGROUND

Improvement in cell throughput in heterogeneous deployment scenarios iscurrently being made through the use of dual connectivity. In dualconnectivity, a User Equipment (UE) is served by serving cellscorresponding to more than one evolved Node B (eNB). Dual connectivityis also referred to as inter-eNB carrier aggregation or inter-noderesource aggregation. In dual connectivity, the UE is connected to aprimary cell (PCell) in a Master eNB (MeNB) and a secondary cell (SCell)in a Secondary eNB (SeNB). A number of approaches have been made toutilize dual connectivity, but each of these approaches has lacked a wayto handle a situation where a radio link failure occurs in one of theeNBs but not the other.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates generally a diagram showing a system 100 with aMaster evolved Node B (MeNB) supporting radio bearers in accordance withsome embodiments.

FIG. 2 illustrates generally a diagram showing a system 200 showing aradio bearer split using a MeNB and a Secondary evolved Node B (SeNB) inaccordance with some embodiments.

FIGS. 3A, 3B, and 3C illustrate generally diagrams showing a WirelessNetwork with a UE operating in a dual connectivity mode in accordancewith some embodiments.

FIG. 4 illustrates generally a diagram showing a byte in a logicalchannel identifier (LCID) in accordance with some embodiments.

FIG. 5 illustrates generally a diagram showing a mobile client device onwhich the configurations and techniques described herein may be deployedin accordance with some embodiments.

FIG. 6 illustrates generally an example of a block diagram of a machine600 upon which any one or more of the techniques (e.g., methodologies)discussed herein can perform in accordance with some embodiments.

In the drawings, which are not necessarily drawn to scale, like numeralsmay describe similar components in different views. Like numerals havingdifferent letter suffixes may represent different instances of similarcomponents. The drawings illustrate generally, by way of example, butnot by way of limitation, various embodiments discussed in the presentdocument.

DETAILED DESCRIPTION

Techniques to handle a radio link failure in dual connectivity settingsare desired. Dual connectivity may refer to systems and methods where aUser Equipment (UE) is served by serving cells corresponding to morethan one evolved Node B (eNB). In an example, a Master eNB (MeNB) and aSecondary eNB (SeNB) may serve a UE. The MeNB may include a primary cell(PCell) and the SeNB may include a secondary cell (SCell). In anexample, for user plane architecture, the UE may be connected to theSeNB directly or indirectly through the MeNB. In another example, aradio bearer, such as a signaling radio bearer (SRB) or a data radiobearer (DRB), may be split between the MeNB and the SeNB. SRBs mayinclude Signaling Radio Bearer 0 (SRB0), Signaling Radio Bearer 1(SRB1), Signaling Radio Bearer 2 (SRB2), or the like, such as may befound in a technical specification similar to the 3GPP TechnicalSpecification (TS) 36.331 “Evolved Universal Terrestrial Radio Access(E-UTRA); Radio Resource Control (RRC) Protocol specification”, (e.g.,release version 11 or later), such as at 4.2.2 “RRC connectionre-establishment”.

FIG. 1 illustrates generally a diagram showing a system 100 with a MeNBsupporting radio bearers in accordance with some embodiments. In anexample, the system 100 uses a MeNB and an SeNB without a bearer split.For example, the MeNB in system 100 may transmit a radio resourcecontrol (RRC) message to a UE but the SeNB may not transmit a RRCmessage. The MeNB may communicate directly with the UE and the SeNB. TheSeNB may communicate to the UE indirectly through the MeNB. The SeNB maynot have SRBs set up to communicate with the UE and may use a DRB tocommunicate with the MeNB.

FIG. 2 illustrates generally a diagram showing a system 200 showing aradio bearer split using a MeNB and a SeNB in accordance with someembodiments. In an example, data may be forwarded by the MeNB using anXn interface and a radio bearer may be split between the MeNB and theSeNB above a radio link control (RLC) layer. Other radio bearers may beconfigured to be used by the MeNB or the SeNB (i.e., not split). If aradio bearer is split, a PDCP PDU of the radio bearer may be transferredto the SeNB by the MeNB using the Xn interface. In an example, using thesystem 200, a RRC message may be transmitted by the MeNB or the SeNB.

FIGS. 1 and 2 illustrate generally, diagrams that show systems that maybe used to implement part or all of any of the embodiments describedbelow.

FIGS. 3A, 3B, and 3C illustrate generally diagrams showing a WirelessNetwork with a UE operating in a dual connectivity mode in accordancewith some embodiments. In an example, a Wireless Network may operate asa 3rd Generation Partnership Project (3GPP) long term evolution (LTE) orLTE-advanced network. For example, FIGS. 3A, 3B, and 3C may representthe interoperation of eNBs and UEs in an LTE network. In an example, aMeNB 302 may connect with a UE 310 over a connection to the MeNB 314when the UE 310 is in range of a PCell 306 served by the MeNB 302. TheUE 310 may use the connection to the MeNB 314 with the MeNB 302 toconnect with the cloud 318 using a cloud connection 320. In a dualconnectivity mode, when the UE 310 is also in range of a SCell 308, theUE 310 may use a SeNB 304 to connect to the internet or the cloud 318.

In an example, the UE 310 may communicate with the cloud 318 using theSeNB 304 directly over a secondary connection 316. In another example,the UE 310 may communicate with the cloud 318 using the SCell 308 andthe SeNB 304 indirectly over a eNB-to-eNB connection 312 and the cloudconnection 320, such as by directly communicating with the SeNB 304 overthe secondary connection 316. The UE 310 may connect with the SeNB 304over the secondary connection 316 when in range of the SCell 308, theSeNB 304 may connect with the MeNB over the eNB-to-eNB connection 312,and the MeNB may connect with the cloud 318 over the cloud connection320. In this example, the UE 310 may communicate with the cloud 318 bysending and receiving data over the various connections.

In an example, the UE 310 may detect a radio link failure on the MeNB302 or the SeNB 304. If no radio link failure is detected by the UE 310on the MeNB 302 or the SeNB 304, the UE may function in dualconnectivity, such as in FIG. 3A. If the UE 310 detects a radio linkfailure on both the MeNB 302 and the SeNB 304, the UE 310 may initiatean RRC connection establishment procedure. For example, the UE 310 mayinitiate a procedure from a technical specification similar to the 3GPPTechnical Specification (TS) 36.331 “Evolved Universal Terrestrial RadioAccess (E-UTRA); Radio Resource Control (RRC) Protocol specification”,(e.g., release version 11 or later), such as at 5.3.7 “RRC connectionre-establishment”. In an example, the UE 310 may identify a radio linkfailure if a timer expires. For example, the timer may be timer T310from a technical specification similar to TS 36.331 described above,such as at 5.5.4.2 “T310 expiry”. In another example, the UE 310 mayidentify a radio link failure if a random access problem indication issent from the MAC. The UE 310 may identify a radio link failure from arandom access problem indication sent from the MAC if specified timersare not running. For example, the timers may be timers T300, T301, T304,or T311 from a technical specification similar to TS 36.331 describedabove. In another example, the UE 310 may identify a radio link failureif an indication is received from the RLC that a number ofretransmissions has exceeded a threshold.

In an example, the UE 310 may detect a radio link failure with the MeNB302 and not on the SeNB 304, such as in FIG. 3B, where the connection tothe MeNB 314 of FIG. 3A fails. The UE 310 may transmit a RRC signalindicating a radio link failure with the MeNB 302 using the secondaryconnection 316 with the SeNB 304. The SeNB 304 may then send the RRCsignal to the MeNB 302 over the eNB-to-eNB connection 312. In anexample, two logical channels may be configured for a specified SRB,with one logical channel for the specified SRB served by the MeNB 302and the other logical channel for the specified SRB served by the SeNB304. The UE 310 may send an indication of the radio link failure on theMeNB 302 by using a logical channel served by the SeNB 304. In anotherexample, there may be one logical channel for a particular SRB, and thelogical channel may be served by the MeNB 302. In this example, the SeNBand the MeNB may communicate over the eNB-to-eNB connection 312 using aDRB, such as a DRB dedicated to eNB-to-eNB communication. The UE 310 mayprevent initiation of, or refrain from initiating, a RRCre-establishment procedure while the SeNB 304 is connected and does nothave a radio link failure. In an example, after the UE 310 detects aradio link failure on the MeNB 302, a timer, such as the T310 timer maybe stopped, if it is running. After the UE 310 detects a radio linkfailure on the MeNB 302, all radio bearers except SRB0 and any DRBsmapped to SeNB 304 may be suspended. After the UE 310 detects a radiolink failure on the MeNB 302, the MAC may be reset. After the UE 310detects a radio link failure on the MeNB 302, a default physical channelconfiguration may be applied, such as the configuration from a technicalspecification similar to TS 36.331 described above, at 9.2.4 “Defaultphysical channel configuration”. After the UE 310 detects a radio linkfailure on the MeNB 302, a default semi-persistent schedulingconfiguration may be applied, such as the configuration from a technicalspecification similar to TS 36.331 described above, at 9.2.3 “Defaultsemi-persistent scheduling configuration”. After the UE 310 detects aradio link failure on the MeNB 302, a default MAC main configuration maybe applied, such as the configuration from a technical specificationsimilar to TS 36.311 described above, at 9.2.2 “Default MAC mainconfiguration.

In an example, after the UE 310 detects a radio link failure on the MeNB302, the MeNB may send a request over the eNB-to-eNB connection 312 tothe SeNB 304 to reconfigure. The SeNB 304 may reconfigure all SRBs,except the SRB0, and all DRBs to be connected to the SeNB 304 andcontinue data operation with the UE 310. The SeNB 304 may providereconfigured radio resource information to the MeNB 302, and then theMeNB 302 may send a RRC connection reconfiguration message through theSeNB 304 to the UE 310 using the relay connections 322A and 322B. Inanother example, the MeNB 302 may perform a handover procedure to theSeNB 304. The MeNB 302 may send a handover command message over the SeNB304 to the UE 310 using the relay connections 322A and 322B.

In an example, when the UE 310 detects a radio link failure with theMeNB 302, UE context may be retained by the MeNB 302. The MeNB 302 maycontinue to maintain the UE context management for the SeNB 304 and theUE 310, and the SeNB 304 may continue to relay information from the UE310 to the MeNB 302. An example of the data flow from the UE 310 to theMeNB 302 may be seen in FIG. 3B, such as using relay connection 322A tosend and receive data with the UE 310 and the SeNB 304 and relayconnection 322B to send and receive data with the SeNB 304 and the MeNB302. Data may sent and received using relay connections 322A and 322B,may also be sent and received with the cloud 318 and the MeNB 302 usingthe cloud connection 320. The connection to the MeNB 314 between the UE310 and the MeNB 302 from FIG. 3A is temporarily or permanently unusablein FIG. 3B, but the UE 310 may still send and receive data with the MeNB302 using the relay connections 322A and 322B as described above. Theconnection to the MeNB 314 may be temporarily unusable if the UE 310 isnot in range of the PCell 306. The UE 310 may later be in range of thePCell 306 or another cell in the MeNB 302. If the MeNB 302 channelcondition with the UE 310 improves, the connection to the MeNB 314 mayresume. In an example, the connection to the MeNB 314 may resume whenthe connection improves, such as using a Radio Resource Management (RRM)measurement. For example, if conditions relating to connection betweenthe UE 310 and the PCell 306 exceed a threshold, the connection to theMeNB 314 may resume. In another example, the UE 310 may monitor thePCell 306, such as by using radio link monitoring and may recover fromthe radio link failure if the UE RRC receives an in-sync indication in asubframe, or if the UE RRC receives in-sync indications in more than oneconsecutive subframe. If the UE 310 monitors the PCell 306 and the PCell306 channel quality remains poor for longer than a specified duration,the MeNB 302 may initiate a handover procedure from the PCell 306. Thehandover procedure may include a handover procedure from the PCell 306to the SCell 308 in the SeNB 304, to another cell in the SeNB 304, or toanother cell not in the SeNB 304. A handover command message may begenerated in RRC in the MeNB 302 and may be sent over the eNB-to-eNBconnection 312 to the SeNB 304. The handover command message may be sentto the UE 310 using the secondary connection 316. The path the handovercommand message may take may also be represented by relay connections322A and 322B.

In an example, the UE 310 may detect a radio link failure on the SeNB304 and not on the MeNB 302, such as in FIG. 3C where the secondaryconnection 316 of FIG. 3A fails. The UE 310 may transmit a RRC signalindicating a radio link failure with the SeNB 304 using the connectionto the MeNB 314, such as by using a logical channel served by the MeNB.The UE 310 may prevent initiation of, or refrain from initiating, a RRCre-establishment procedure while the MeNB 302 is connected and does nothave a radio link failure. In an example, after the UE 310 detects aradio link failure on the SeNB 304, a timer, such as the T310 timer maybe stopped, if it is running. After the UE 310 detects a radio linkfailure on the SeNB 304, all radio bearers except radio bearers mappedto MeNB 302 may be suspended. After the UE 310 detects a radio linkfailure on the SeNB 304, the MAC may be reset. After the UE 310 detectsa radio link failure on the SeNB 304, a default physical channelconfiguration may be applied, such as the configuration from a technicalspecification similar to TS 36.331 described above, at 9.2.4 “Defaultphysical channel configuration”. After the UE 310 detects a radio linkfailure on the SeNB 304, a default semi-persistent schedulingconfiguration may be applied, such as the configuration from a technicalspecification similar to TS 36.331 described above, at 9.2.3 “Defaultsemi-persistent scheduling configuration”. After the UE 310 detects aradio link failure on the SeNB 304, a default MAC main configuration maybe applied, such as the configuration from a technical specificationsimilar to TS 36.311 described above, at 9.2.2 “Default MAC mainconfiguration.

In an example, the MeNB 302 may send a request to the SeNB 304 torelease serving cells mapped to the SeNB 304, such as the SCell 308. TheSeNB 304 may later be added in a dual connection with the MeNB 302 ifthe channel situation in the SeNB 304 improves. In another example, theSeNB 304 release or addition may not involve additional signaling to thecore network (e.g., the cloud 318). In an example, the MeNB 302 may senda RRC connection reconfiguration message to the UE 310 over theconnection to the MeNB 314 to remove the SCell 308 (or any othersecondary cells) mapped to the SeNB. The RRC connection reconfigurationmessage may also request the reconfiguration of radio bearers served bythe SeNB 304.

A UE 310 may initialize a contention-based or a non-contention-basedrandom access procedure to attempt to contact a network. In an example,the UE may use a contention-based random access procedure or anon-contention-based random access procedure for the PCell 306 or theSCell 308 in dual connectivity. A contention-based random accessprocedure is a random access procedure where the UE is sending a requestthat may collide with other UEs making other random access requests. Anon-contention-based random access procedure differs in that the networkmay indicate a unique identifier for the UE's request, such that therequest is less likely to collide with other UEs making other randomaccess requests.

If a maximum number of preamble transmissions is reached in a randomaccess procedure (contention-based or non-contention-based) when the UE310 is in a non-dual connectivity environment, the UE 310 may indicate arandom access problem to upper layers. When the UE 310 is in a dualconnectivity environment, if the random access procedure fails in theMeNB 302 (e.g., a preamble transmission counter exceeds a threshold),the UE may indicate a random access problem to upper layers.

In an example, in order to notify the network or the upper layers that arandom access procedure has failed in the SeNB 304, the UE 310 mayindicate a random access problem to upper layers or send a random accessproblem indication to the MeNB 302, such as over a UE random accessproblem connection 324A. For example, the UE 310 may indicate a randomaccess problem to upper layers if a contention-based random accessprocedure for the SeNB 304, such as on the SCell 308 corresponding tothe SeNB 304, fails (e.g., a maximum number of attempts is reached or athreshold is exceeded, such asPREAMBLE_TRANSMISSION_COUNTER=preambleTransMax+1). In an example, therandom access procedure for the SeNB 304 may be a non-contention-basedrandom access procedure. The UE 310 may indicate a random access problemto upper layers, such as the RRC layer and the RRC may declare a radiolink failure in the SCell 308 or the SeNB 304 based on the indicationfrom the UE 310 of the random access problem. The MeNB 302 may transmitto the SeNB 304 information about the random access problem using an eNBrandom access problem connection 324B.

In another example, the UE 310 may send a random access problemindication to the MeNB 302 indicating that the random access procedurefor the SeNB 304 has failed. For example, the UE 310 may indicate arandom access problem to the MeNB 302 if a contention-based randomaccess procedure for the SeNB 304, such as on the SCell 308corresponding to the SeNB 304, fails (e.g., a maximum number of attemptsis reached or a threshold is exceeded, such asPREAMBLE_TRANSMISSION_COUNTER=preambleTransMax+1). In an example, therandom access procedure for the SeNB 304 may be a non-contention-basedrandom access procedure. In an example, the UE 310 may indicate to theMeNB 302 that a random access procedure failure has occurred with theSeNB 304 using RRC signaling. In another example, the UE 310 may use aMedium Access Control (MAC) control element (MAC CE) to send anindication of a random access problem. The MeNB 302 may transmit to theSeNB 304 information about the random access problem using an eNB randomaccess problem connection 324B. For example, one value in a logicalchannel identifier (LCID) may be used to represent the random accessproblem in the SeNB 304. In an example, the value may be an index valuein the LCID for an upload scheduler (UL-SCH), such as a value of 11000,as shown in Table 1 below. For example, the value may be added to atechnical specification similar to the 3GPP Technical Specification (TS)36.321 “Evolved Universal Terrestrial Radio Access (E-UTRA); MediumAccess Control (MAC) protocol specification”, (e.g., release version 11or later). For example, such a table may be provided in section 6.2.1 ofTS 36.321. In addition to the values that are currently defined in theTS 36.321, for example, a new value may be defined for the random accessproblem in SeNB.

TABLE 1 Values of LCID for UL-SCH in LTE as can be added to section6.2.1 of TS 36.321. Index LCID Values 00000 CCCH 00001-01010 Identity ofthe logical channel 01011-10111 Reserved 11000 Random Access Problem inSeNB 11001 Extended Power Headroom Report 11010 Power Headroom Report11011 C-RNTI 11100 Truncated BSR 11101 Short BSR 11110 Long BSR 11111Padding

In an example, the MAC CE may have a fixed size of zero bytes. Inanother example, the MAC CE may have one or more bytes to indicate aradio link failure in the SeNB 304. For example, the LCID 11000 in Table1 above may be used to represent a radio link problem in SeNB 304 MACCE, and the byte may have a format, such as the format in FIG. 4.

FIG. 4 illustrates generally a diagram showing a byte in a logicalchannel identifier (LCID) in accordance with some embodiments. In anexample, in FIG. 4, “R” may represent a reserved bit, “RA” may representa random access problem in SeNB, “RL” may indicate a RLC error in SeNB,or “QL” may indicate a radio link monitoring problem in SeNB. Forexample, if “RA” is set to one, that may indicate there is a randomaccess problem in SeNB and if “RA” is set to zero, that may indicatethere is not a random access problem in SeNB. For example, if “RL” isset to one, that may indicate there is a RLC error in SeNB and if “RL”is set to zero, that may indicate there is not a RLC error in SeNB. Forexample, if “QL” is set to one, that may indicate there is a radio linkmonitoring problem in SeNB and if “QL” is set to zero, that may indicatethere is not a radio link monitoring problem in SeNB.

FIG. 5 illustrates generally a diagram showing a mobile client device onwhich the configurations and techniques described herein may be deployedin accordance with some embodiments. FIG. 5 provides an exampleillustration of a mobile device 500, such as a user equipment (UE), amobile station (MS), a mobile wireless device, a mobile communicationdevice, a tablet, a handset, or other type of mobile wireless computingdevice. The mobile device 500 may include one or more antennas 508within housing 502 that are configured to communicate with a hotspot,base station (BS), an eNB, or other type of WLAN or WWAN access point.The mobile device may be configured to communicate using multiplewireless communication standards, including standards selected from 3GPPLTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and Wi-Fistandard definitions. The mobile device 500 may communicate usingseparate antennas for each wireless communication standard or sharedantennas for multiple wireless communication standards. The mobiledevice 500 may communicate in a WLAN, a WPAN, and/or a WWAN.

FIG. 5 also provides an illustration of a microphone 520 and one or morespeakers 512 that may be used for audio input and output from the mobiledevice 500. A display screen 504 may be a liquid crystal display (LCD)screen, or other type of display screen such as an organic lightemitting diode (OLED) display. The display screen 504 may be configuredas a touch screen. The touch screen may use capacitive, resistive, oranother type of touch screen technology. An application processor 514and a graphics processor 518 may be coupled to internal memory 516 toprovide processing and display capabilities. A non-volatile memory port510 may also be used to provide data input/output options to a user. Thenon-volatile memory port 510 may also be used to expand the memorycapabilities of the mobile device 500. A keyboard 506 may be integratedwith the mobile device 500 or wirelessly connected to the mobile device500 to provide additional user input. A virtual keyboard may also beprovided using the touch screen. A camera 522 located on the front(display screen) side or the rear side of the mobile device 500 may alsobe integrated into the housing 502 of the mobile device 500.

FIG. 6 illustrates generally an example of a block diagram of a machine600 upon which any one or more of the techniques (e.g., methodologies)discussed herein can perform in accordance with some embodiments. Inalternative embodiments, the machine 600 can operate as a standalonedevice or can be connected (e.g., networked) to other machines. In anetworked deployment, the machine 600 can operate in the capacity of aserver machine, a client machine, or both in server-client networkenvironments. In an example, the machine 600 can act as a peer machinein peer-to-peer (P2P) (or other distributed) network environment. Themachine 600 can be a personal computer (PC), a tablet PC, a set-top box(STB), a personal digital assistant (PDA), a mobile telephone, a webappliance, a network router, switch or bridge, or any machine capable ofexecuting instructions (sequential or otherwise) that specify actions tobe taken by that machine. Further, while only a single machine isillustrated, the term “machine” shall also be taken to include anycollection of machines that individually or jointly execute a set (ormultiple sets) of instructions to perform any one or more of themethodologies discussed herein, such as cloud computing, software as aservice (SaaS), other computer cluster configurations.

Examples, as described herein, can include, or can operate on, logic ora number of components, modules, or mechanisms. Modules are tangibleentities (e.g., hardware) capable of performing specified operationswhen operating. A module includes hardware. In an example, the hardwarecan be specifically configured to carry out a specific operation (e.g.,hardwired). In an example, the hardware can include configurableexecution units (e.g., transistors, circuits, etc.) and a computerreadable medium containing instructions, where the instructionsconfigure the execution units to carry out a specific operation when inoperation. The configuring can occur under the direction of theexecutions units or a loading mechanism. Accordingly, the executionunits are communicatively coupled to the computer readable medium whenthe device is operating. In this example, the execution units can be amember of more than one module. For example, under operation, theexecution units can be configured by a first set of instructions toimplement a first module at one point in time and reconfigured by asecond set of instructions to implement a second module.

Machine (e.g., computer system) 600 can include a hardware processor 602(e.g., a central processing unit (CPU), a graphics processing unit(GPU), a hardware processor core, or any combination thereof), a mainmemory 604 and a static memory 606, some or all of which can communicatewith each other via an interlink (e.g., bus) 608. The machine 600 canfurther include a display unit 610, an alphanumeric input device 612(e.g., a keyboard), and a user interface (UI) navigation device 614(e.g., a mouse). In an example, the display unit 610, alphanumeric inputdevice 612 and UI navigation device 614 can be a touch screen display.The machine 600 can additionally include a storage device (e.g., driveunit) 616, a signal generation device 618 (e.g., a speaker), a networkinterface device 620, and one or more sensors 621, such as a globalpositioning system (GPS) sensor, compass, accelerometer, or othersensor. The machine 600 can include an output controller 628, such as aserial (e.g., universal serial bus (USB), parallel, or other wired orwireless (e.g., infrared (IR), near field communication (NFC), etc.)connection to communicate or control one or more peripheral devices(e.g., a printer, card reader, etc.).

The storage device 616 can include a machine readable medium 622 that isnon-transitory on which is stored one or more sets of data structures orinstructions 624 (e.g., software) embodying or utilized by any one ormore of the techniques or functions described herein. The instructions624 can also reside, completely or at least partially, within the mainmemory 604, within static memory 606, or within the hardware processor602 during execution thereof by the machine 600. In an example, one orany combination of the hardware processor 602, the main memory 604, thestatic memory 606, or the storage device 616 can constitute machinereadable media.

While the machine readable medium 622 is illustrated as a single medium,the term “machine readable medium” can include a single medium ormultiple media (e.g., a centralized or distributed database, and/orassociated caches and servers) configured to store the one or moreinstructions 624.

The term “machine readable medium” can include any medium that iscapable of storing, encoding, or carrying instructions for execution bythe machine 600 and that cause the machine 600 to perform any one ormore of the techniques of the present disclosure, or that is capable ofstoring, encoding or carrying data structures used by or associated withsuch instructions. Non-limiting machine readable medium examples caninclude solid-state memories, and optical and magnetic media. In anexample, a massed machine readable medium comprises a machine readablemedium with a plurality of particles having invariant (e.g., rest) mass.Accordingly, massed machine-readable media are not transitorypropagating signals. Specific examples of massed machine readable mediacan include: non-volatile memory, such as semiconductor memory devices(e.g., Electrically Programmable Read-Only Memory (EPROM), ElectricallyErasable Programmable Read-Only Memory (EEPROM)) and flash memorydevices; magnetic disks, such as internal hard disks and removabledisks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

The instructions 624 can further be transmitted or received over acommunications network 626 using a transmission medium via the networkinterface device 620 utilizing any one of a number of transfer protocols(e.g., frame relay, internet protocol (IP), transmission controlprotocol (TCP), user datagram protocol (UDP), hypertext transferprotocol (HTTP), etc.). Example communication networks can include alocal area network (LAN), a wide area network (WAN), a packet datanetwork (e.g., the Internet), mobile telephone networks (e.g., cellularnetworks), Plain Old Telephone (POTS) networks, and wireless datanetworks (e.g., Institute of Electrical and Electronics Engineers (IEEE)802.11 family of standards known as Wi-Fi®, IEEE 802.16 family ofstandards known as WiMax®), IEEE 802.15.4 family of standards,peer-to-peer (P2P) networks, among others. In an example, the networkinterface device 620 can include one or more physical jacks (e.g.,Ethernet, coaxial, or phone jacks) or one or more antennas to connect tothe communications network 626. In an example, the network interfacedevice 620 can include a plurality of antennas to wirelessly communicateusing at least one of single-input multiple-output (SIMO),multiple-input multiple-output (MIMO), or multiple-input single-output(MISO) techniques. The term “transmission medium” shall be taken toinclude any intangible medium that is capable of storing, encoding orcarrying instructions for execution by the machine 600, and includesdigital or analog communications signals or other intangible medium tofacilitate communication of such software.

Various Notes & Examples

Additional examples of the presently described method, system, anddevice embodiments are suggested according to the structures andtechniques described herein. Other non-limiting examples can beconfigured to operate separately, or can be combined in any permutationor combination with any one or more of the other examples provided aboveor throughout the present disclosure.

Example 1 includes the subject matter embodied by a first evolved Node B(eNB), the first eNB connected to a User Equipment (UE), the eNBcomprising: hardware processing circuitry arranged to: receive, from theUE, an indication of a Radio Link Failure at a second eNB, the UE in adual connectivity state with the first eNB and the second eNB,communicate to the second eNB a command to suspend at least one radiobearer used by the second eNB.

In Example 2, the subject matter of Example 1 can optionally includewherein the first eNB is a Master eNB (MeNB) and the second eNB is aSecondary eNB (SeNB), and wherein the MeNB is associated with a PrimaryCell (PCell) and the SeNB is associated with a Secondary Cell (SCell).

In Example 3, the subject matter of one or any combination of Examples1-2 can optionally include wherein operations to suspend the at leastone radio bearer used by the second eNB include operations to suspendall radio bearers used by SeNB.

In Example 4, the subject matter of one or any combination of Examples1-3 can optionally include wherein the hardware processing circuitry ofthe MeNB is further arranged to transmit a Radio Resource Controlreconfiguration message to the UE to remove the SCell from a set ofcells serving the UE to suspend the at least one radio bearer.

In Example 5, the subject matter of one or any combination of Examples1-4 can optionally include wherein the first eNB is a Secondary eNB(SeNB) and the second eNB is a Master eNB (MeNB), and wherein the MeNBis associated with a Primary Cell (PCell) and the SeNB is associatedwith a Secondary Cell (SCell).

In Example 6, the subject matter of one or any combination of Examples1-5 can optionally include wherein operations to suspend the at leastone radio bearer used by the second eNB include operations to suspend aSignaling Radio Bearer 1 (SRB1) and a Signaling Radio Bearer 2 (SRB2)used by the MeNB.

In Example 7, the subject matter of one or any combination of Examples1-6 can optionally include wherein the hardware processing circuitry ofthe SeNB is further arranged to relay a Radio Resource Controlreconfiguration message from the MeNB to the UE to suspend the at leastone radio bearer.

In Example 8, the subject matter of one or any combination of Examples1-7 can optionally include wherein the hardware processing circuitry ofthe SeNB is further arranged to receive instructions to initiate ahandover from the MeNB to suspend the at least one radio bearer.

In Example 9, the subject matter of one or any combination of Examples1-8 can optionally include wherein the hardware processing circuitry ofthe SeNB is further arranged to use a UE context for the UE, the UEcontext maintained by the MeNB.

In Example 10, the subject matter of one or any combination of Examples1-9 can optionally include wherein the hardware processing circuitry ofthe SeNB is further arranged to receive the Radio Link Failureindication over a logical channel.

In Example 11, the subject matter of one or any combination of Examples1-10 can optionally include wherein the MeNB is further arranged toreceive an indication of a random access problem from the UE.

In Example 12, the subject matter of one or any combination of Examples1-11 can optionally include wherein the indication is received by theMeNB using a Radio Resource Control (RRC) message.

In Example 13, the subject matter of one or any combination of Examples1-12 can optionally include wherein the indication is received by theMeNB using a MAC control element.

In Example 14, the subject matter of one or any combination of Examples1-13 can optionally include wherein the MAC control element has zerobytes.

In Example 15, the subject matter of one or any combination of Examples1-14 can optionally include wherein the MAC control element includesinformation indicating: a random access problem in the SeNB, a radiolink control error in the SeNB, or a radio link monitoring error in theSeNB.

Example 16 includes the subject matter embodied by User Equipment (UE)adapted for communication with an evolved Node B (eNB), the UEcomprising: a transceiver arranged to transmit and receive communicationwith a Master eNB (MeNB) and a Secondary eNB (SeNB), and a processor,coupled to the transceiver, arranged to perform operations in connectionwith a connection to a MeNB and a connection to a SeNB: determine thatone of a connection to the MeNB and a connection to the SeNB has a RadioLink Failure, determine that the other one of the connection to the MeNBand the connection to the SeNB does not have a Radio Link Failure, andprevent initiation of a Radio Resource Control (RRC) re-establishmentprocedure while the other one of the connection to the MeNB and theconnection to the SeNB does not have a Radio Link Failure.

In Example 17, the subject matter of Example 16 can optionally includewherein the connection that has a Radio Link Failure is the MeNB and theconnection that remains connected is the SeNB, and wherein the MeNB isassociated with a Primary Cell (PCell) and the SeNB is associated with aSecondary Cell (SCell).

In Example 18, the subject matter of one or any combination of Examples16-17 can optionally include wherein the UE is further arranged toreceive a Radio Resource Control (RRC) reconfiguration message from theMeNB to remove the SCell.

In Example 19, the subject matter of one or any combination of Examples16-18 can optionally include wherein the UE is further arranged totransmit a Radio Resource Control (RRC) message to the MeNB indicatingthat the SeNB has a Radio Link Failure.

In Example 20, the subject matter of one or any combination of Examples16-19 can optionally include wherein the UE is further arranged totransmit the RRC message over a logical channel.

In Example 21, the subject matter of one or any combination of Examples16-20 can optionally include wherein the connection that has a RadioLink Failure is the SeNB and the connection that remains connected isthe MeNB, and wherein the MeNB is associated with a Primary Cell (PCell)and the SeNB is associated with a Secondary Cell (SCell).

In Example 22, the subject matter of one or any combination of Examples16-21 can optionally include wherein the UE is further arranged toreceive a Radio Resource Control reconfiguration message originatingfrom the MeNB sent through the SeNB.

In Example 23, the subject matter of one or any combination of Examples16-22 can optionally include wherein the UE is further arranged toreceive a handover command message originating from the MeNB through theSeNB.

In Example 24, the subject matter of one or any combination of Examples16-23 can optionally include wherein the UE is further arranged toreceive a handover command message originating from the MeNB through anew cell, wherein the new cell is not the PCell or the SCell.

In Example 25, the subject matter of one or any combination of Examples16-24 can optionally include wherein the UE is further arranged to use aUE context, the UE context maintained by the MeNB.

In Example 26, the subject matter of one or any combination of Examples16-25 can optionally include wherein the UE is further arranged toreconnect to the MeNB when a MeNB channel condition exceeds a threshold.

In Example 27, the subject matter of one or any combination of Examples16-26 can optionally include wherein the UE is further arranged tomonitor the PCell after determining that the MeNB has a Radio LinkFailure.

In Example 28, the subject matter of one or any combination of Examples16-27 can optionally include wherein the UE is further arranged totransmit a radio resource control (RRC) message to the SeNB indicatingthat the MeNB has a Radio Link Failure.

In Example 29, the subject matter of one or any combination of Examples16-28 can optionally include wherein the UE is further arranged totransmit the RRC message over a logical channel.

In Example 30, the subject matter of one or any combination of Examples16-29 can optionally include wherein the UE is further arranged toindicate a Random Access problem to an upper layer.

In Example 31, the subject matter of one or any combination of Examples16-30 can optionally include wherein the UE is further arranged totransmit an indication of a random access problem to the MeNB.

In Example 32, the subject matter of one or any combination of Examples16-31 can optionally include wherein the UE uses a MAC control elementto transmit the indication.

In Example 33, the subject matter of one or any combination of Examples16-32 can optionally include wherein the MAC control element has zerobytes.

In Example 34, the subject matter of one or any combination of Examples16-33 can optionally include wherein the MAC control element includesinformation indicating: a random access problem in the SeNB, a radiolink control error in the SeNB, or a radio link monitoring error in theSeNB.

In Example 35, the subject matter of one or any combination of Examples16-34 can optionally include wherein the UE uses a Radio ResourceControl (RRC) message to indicate the random access problem to the MeNB.

Example 36 includes the subject matter embodied by a method performed bycircuitry of a User Equipment (UE) comprising: connecting, at a UserEquipment (UE), to a Master evolved Node B (eNB) (MeNB), connecting, atthe UE, to a Secondary eNB (SeNB), determining, at the UE, that one ofthe connections has a Radio Link Failure, determining, at the UE, thatthe other of the connections remains connected to the UE, and refrainingfrom initiating a Radio Resource Control (RRC) re-establishmentprocedure while at least one of the connections does not have a RadioLink Failure.

In Example 37, the subject matter of Example 36 can optionally includewherein the connection that has a Radio Link Failure is the MeNB and theconnection that remains connected is the SeNB, and wherein the MeNB isassociated with a Primary Cell (PCell) and the SeNB is associated with aSecondary Cell (SCell).

In Example 38, the subject matter of one or any combination of Examples36-37 can optionally include further comprising, receiving, at the UE, aRadio Resource Control reconfiguration message from the MeNB to removethe SCell from a set of cells serving the UE.

In Example 39, the subject matter of one or any combination of Examples36-38 can optionally include further comprising, transmitting a radioresource control (RRC) message to the MeNB indicating that the SeNB hasa Radio Link Failure.

In Example 40, the subject matter of one or any combination of Examples36-39 can optionally include wherein transmitting the RRC messageincludes transmitting the RRC message over a logical channel.

In Example 41, the subject matter of one or any combination of Examples36-40 can optionally include wherein the connection that has a RadioLink Failure is the SeNB and the connection that remains connected isthe MeNB, and wherein the MeNB is associated with a Primary Cell (PCell)and the SeNB is associated with a Secondary Cell (SCell).

In Example 42, the subject matter of one or any combination of Examples36-41 can optionally include further comprising, receiving, at the UE, aRadio Resource Control (RRC) reconfiguration message originating fromthe MeNB sent through the SeNB.

In Example 43, the subject matter of one or any combination of Examples36-42 can optionally include further comprising, receiving, at the UE, ahandover command message originating from the MeNB through the SeNB.

In Example 44, the subject matter of one or any combination of Examples36-43 can optionally include further comprising, receiving, at the UE, ahandover command message originating from the MeNB through a new cell,wherein the new cell is not the PCell or the SCell.

In Example 45, the subject matter of one or any combination of Examples36-44 can optionally include further comprising, using a UE context, theUE context maintained by the MeNB.

In Example 46, the subject matter of one or any combination of Examples36-45 can optionally include further comprising, reconnecting, at theUE, to the MeNB when a MeNB channel condition exceeds a threshold.

In Example 47, the subject matter of one or any combination of Examples36-46 can optionally include further comprising, monitoring the PCellafter determining that the MeNB has a Radio Link Failure.

In Example 48, the subject matter of one or any combination of Examples36-47 can optionally include further comprising, transmitting a RadioResource Control (RRC) message to the SeNB indicating that the MeNB hasa Radio Link Failure.

In Example 49, the subject matter of one or any combination of Examples36-48 can optionally include wherein transmitting the RRC messageincludes transmitting the RRC message over a logical channel.

In Example 50, the subject matter of one or any combination of Examples36-49 can optionally include further comprising, indicating a RandomAccess problem to an upper layer.

In Example 51, the subject matter of one or any combination of Examples36-50 can optionally include further comprising, transmitting anindication of a random access problem to the MeNB.

In Example 52, the subject matter of one or any combination of Examples36-51 can optionally include wherein transmitting the indicationincludes transmitting the indication using a MAC control element.

In Example 53, the subject matter of one or any combination of Examples36-52 can optionally include wherein the MAC control element has zerobytes.

In Example 54, the subject matter of one or any combination of Examples36-53 can optionally include wherein the MAC control element includesinformation indicating: a random access problem in the SeNB, a radiolink control error in the SeNB, or a radio link monitoring error in theSeNB.

In Example 55, the subject matter of one or any combination of Examples36-54 can optionally include wherein indicating the random accessproblem to the MeNB includes using a Radio Resource Control (RRC)message.

In Example 56, the subject matter of one or any combination of Examples36-55 can optionally include an apparatus comprising means forperforming any of the methods of Examples 36-55.

Example 57 includes the subject matter embodied by an apparatuscomprising: means for connecting, at a User Equipment (UE), to a Masterevolved Node B (MeNB), means for connecting, at the UE, to a SecondaryeNB (SeNB), means for determining, at the UE, that one of theconnections has a Radio Link Failure, means for determining, at the UE,that the other of the connections remains connected to the UE, and meansfor refraining from initiating a Radio Resource Control (RRC)re-establishment procedure while at least one of the connections doesnot have a Radio Link Failure.

In Example 58, the subject matter of one or any combination of Examples36-55 can optionally include at least one machine-readable mediumincluding instructions for operation of a computer system, which whenexecuted by a machine, cause the machine to perform any of the methodsof Examples 36-55.

Example 59 includes the subject matter embodied by at least onemachine-readable medium including instructions for operation of acomputing system, which when executed by a machine, cause the machineto: connect, at a User Equipment (UE), to a Master evolved Node B(MeNB), connect, at the UE, to a Secondary eNB (SeNB), determine, at theUE, that one of the connections has a Radio Link Failure, determine, atthe UE, that the other of the connections does not have a Radio LinkFailure, and refrain from initiating a Radio Resource Control (RRC)re-establishment procedure while at least one of the connections doesnot have a Radio Link Failure.

In Example 60, the subject matter of Example 59 can optionally includewherein the connection that has a Radio Link Failure is the MeNB and theconnection that remains connected is the SeNB, and wherein the MeNB isassociated with a Primary Cell (PCell) and the SeNB is associated with aSecondary Cell (SCell).

In Example 61, the subject matter of one or any combination of Examples59-60 can optionally include further comprising operations to receive,at the UE, a Radio Resource Control reconfiguration message from theMeNB to remove the SCell from a set of cells serving the UE.

In Example 62, the subject matter of one or any combination of Examples59-61 can optionally include further comprising, operations to transmita radio resource control (RRC) message to the MeNB indicating that theSeNB has a Radio Link Failure.

In Example 63, the subject matter of one or any combination of Examples59-62 can optionally include wherein to transmit the RRC messageincludes to transmit the RRC message over a logical channel.

In Example 64, the subject matter of one or any combination of Examples59-63 can optionally include wherein the connection that has a RadioLink Failure is the SeNB and the connection that remains connected isthe MeNB, and wherein the MeNB is associated with a Primary Cell (PCell)and the SeNB is associated with a Secondary Cell (SCell).

In Example 65, the subject matter of one or any combination of Examples59-64 can optionally include further comprising, operations to receive,at the UE, a Radio Resource Control (RRC) reconfiguration messageoriginating from the MeNB sent through the SeNB.

In Example 66, the subject matter of one or any combination of Examples59-65 can optionally include further comprising, operations to receive,at the UE, a handover command message originating from the MeNB throughthe SeNB.

In Example 67, the subject matter of one or any combination of Examples59-66 can optionally include further comprising, operations to receive,at the UE, a handover command message originating from the MeNB througha new cell, wherein the new cell is not the PCell or the SCell.

In Example 68, the subject matter of one or any combination of Examples59-67 can optionally include further comprising, operations to use a UEcontext, the UE context maintained by the MeNB.

In Example 69, the subject matter of one or any combination of Examples59-68 can optionally include further comprising, operations toreconnect, at the UE, to the MeNB when a MeNB channel condition exceedsa threshold.

In Example 70, the subject matter of one or any combination of Examples59-69 can optionally include further comprising, operations to monitorthe PCell after determining that the MeNB has a Radio Link Failure.

In Example 71, the subject matter of one or any combination of Examples59-70 can optionally include further comprising, operations to transmita Radio Resource Control (RRC) message to the SeNB indicating that theMeNB has a Radio Link Failure.

In Example 72, the subject matter of one or any combination of Examples59-71 can optionally include wherein to transmit the RRC messageincludes to transmit the RRC message over a logical channel.

In Example 73, the subject matter of one or any combination of Examples59-72 can optionally include further comprising, operations to indicatea Random Access problem to an upper layer.

In Example 74, the subject matter of one or any combination of Examples59-73 can optionally include further comprising, operations to transmitan indication of a random access problem to the MeNB.

In Example 75, the subject matter of one or any combination of Examples59-74 can optionally include wherein to transmit the indication includesto transmit the indication using a MAC control element.

In Example 76, the subject matter of one or any combination of Examples59-75 can optionally include wherein the MAC control element has zerobytes.

In Example 77, the subject matter of one or any combination of Examples59-76 can optionally include wherein the MAC control element includesinformation indicating: a random access problem in the SeNB, a radiolink control error in the SeNB, or a radio link monitoring error in theSeNB.

In Example 78, the subject matter of one or any combination of Examples59-77 can optionally include wherein to indicate the random accessproblem to the MeNB includes to indicate the random access problem tothe MeNB using a Radio Resource Control (RRC) message.

Example 79 includes the subject matter embodied by a method performed bycircuitry of a first evolved Node B (eNB) comprising: connecting, at thefirst eNB, to a User Equipment (UE), wherein the UE is arranged toconnect to a second eNB, receiving, at the first eNB, from the UE, anindication of a Radio Link Failure at the second eNB, and suspending atleast one radio bearer used by the second eNB.

In Example 80, the subject matter of Example 79 can optionally includewherein the first eNB is a Master eNB (MeNB) and the second eNB is aSecondary eNB (SeNB), and wherein the MeNB is associated with a PrimaryCell (PCell) and the SeNB is associated with a Secondary Cell (SCell).

In Example 81, the subject matter of one or any combination of Examples79-80 can optionally include wherein suspending at least one radiobearer used by the second eNB includes suspending all radio bearers usedby SeNB.

In Example 82, the subject matter of one or any combination of Examples79-81 can optionally include further comprising, transmitting a RadioResource Control (RRC) reconfiguration message to the UE to remove theSCell.

In Example 83, the subject matter of one or any combination of Examples79-82 can optionally include wherein the first eNB is a Secondary eNB(SeNB) and the second eNB is a Master eNB (MeNB), and wherein the MeNBis associated with a Primary Cell (PCell) and the SeNB is associatedwith a Secondary Cell (SCell).

In Example 84, the subject matter of one or any combination of Examples79-83 can optionally include wherein suspending at least one radiobearer used by the second eNB includes suspending a Signaling RadioBearer 1 (SRB1) and a Signaling Radio Bearer 2 (SRB2) used by the MeNB.

In Example 85, the subject matter of one or any combination of Examples79-84 can optionally include further comprising, relaying a RadioResource Control reconfiguration message from the MeNB to the UE tosuspend the at least one radio bearer.

In Example 86, the subject matter of one or any combination of Examples79-85 can optionally include further comprising, receiving instructionsto initiate a handover procedure from the MeNB to suspend the at leastone radio bearer.

In Example 87, the subject matter of one or any combination of Examples79-86 can optionally include further comprising, using a UE context forthe UE, the UE context maintained by the MeNB.

In Example 88, the subject matter of one or any combination of Examples79-87 can optionally include wherein receiving the Radio Link Failureindication includes receiving the Radio Link Failure indication over alogical channel.

In Example 89, the subject matter of one or any combination of Examples79-88 can optionally include wherein the MeNB is further arranged toreceive an indication of a random access problem from the UE.

In Example 90, the subject matter of one or any combination of Examples79-89 can optionally include wherein MeNB is further arranged to receivethe indication using a Radio Resource Control (RRC) message.

In Example 91, the subject matter of one or any combination of Examples79-90 can optionally include wherein MeNB is further arranged to receivethe indication by using a MAC control element.

In Example 92, the subject matter of one or any combination of Examples79-91 can optionally include wherein the MAC control element has zerobytes.

In Example 93, the subject matter of one or any combination of Examples79-92 can optionally include wherein the MAC control element includesinformation indicating: a random access problem in the SeNB, a radiolink control error in the SeNB, or a radio link monitoring error in theSeNB.

In Example 94, the subject matter of one or any combination of Examples79-93 can optionally include an apparatus comprising means forperforming any of the methods of claims 79-93.

Example 95 includes the subject matter embodied by an apparatuscomprising: means for connecting, at a first evolved Node B (eNB), to aUser Equipment (UE), wherein the UE is arranged to connect to a secondeNB, means for receiving, at the first eNB, from the UE, an indicationof a Radio Link Failure at the second eNB; and means for suspending atleast one radio bearer used by the second eNB.

In Example 96, the subject matter of one or any combination of Examples79-93 can optionally include at least one machine-readable mediumincluding instructions for operation of a computer system, which whenexecuted by a machine, cause the machine to perform any of the methodsof claims 79-93.

Example 97 includes the subject matter embodied by at least onemachine-readable medium including instructions for operation of acomputing system, which when executed by a machine, cause the machineto: connect, at a first evolved Node B (eNB), to a User Equipment (UE),wherein the UE is arranged to connect to a second eNB, receive, at thefirst eNB, from the UE, an indication of a Radio Link Failure at thesecond eNB, and suspend at least one radio bearer used by the secondeNB.

In Example 98, the subject matter of Example 97 can optionally includewherein the first eNB is a Master eNB (MeNB) and the second eNB is aSecondary eNB (SeNB), and wherein the MeNB is associated with a PrimaryCell (PCell) and the SeNB is associated with a Secondary Cell (SCell).

In Example 99, the subject matter of one or any combination of Examples97-98 can optionally include wherein to suspend the at least one radiobearer used by the second eNB includes to suspend all radio bearers usedby SeNB.

In Example 100, the subject matter of one or any combination of Examples97-99 can optionally include further comprising, operations to transmita Radio Resource Control (RRC) reconfiguration message to the UE toremove the SCell.

In Example 101, the subject matter of one or any combination of Examples97-100 can optionally include wherein the first eNB is a Secondary eNB(SeNB) and the second eNB is a Master eNB (MeNB), and wherein the MeNBis associated with a Primary Cell (PCell) and the SeNB is associatedwith a Secondary Cell (SCell).

In Example 102, the subject matter of one or any combination of Examples97-101 can optionally include wherein to suspend the at least one radiobearer used by the second eNB includes to suspend a Signaling RadioBearer 1 (SRB1) and a Signaling Radio Bearer 2 (SRB2) used by the MeNB.

In Example 103, the subject matter of one or any combination of Examples97-102 can optionally include further comprising, operations to relay aRadio Resource Control reconfiguration message from the MeNB to the UEto suspend the at least one radio bearer.

In Example 104, the subject matter of one or any combination of Examples97-103 can optionally include further comprising, operations to receiveinstructions to initiate a handover procedure from the MeNB to suspendthe at least one radio bearer.

In Example 105, the subject matter of one or any combination of Examples97-104 can optionally include further comprising, operations to use a UEcontext for the UE, the UE context maintained by the MeNB.

In Example 106, the subject matter of one or any combination of Examples97-105 can optionally include wherein to receive the Radio Link Failureindication includes to receive the Radio Link Failure indication over alogical channel.

In Example 107, the subject matter of one or any combination of Examples97-106 can optionally include wherein the MeNB is further arranged toreceive an indication of a random access problem from the UE.

In Example 108, the subject matter of one or any combination of Examples97-107 can optionally include wherein MeNB is further arranged toreceive the indication using a Radio Resource Control (RRC) message.

In Example 109, the subject matter of one or any combination of Examples97-108 can optionally include wherein MeNB is further arranged toreceive the indication by using a MAC control element.

In Example 110, the subject matter of one or any combination of Examples97-109 can optionally include wherein the MAC control element has zerobytes.

In Example 111, the subject matter of one or any combination of Examples97-110 can optionally include wherein the MAC control element includesinformation indicating: a random access problem in the SeNB, a radiolink control error in the SeNB, or a radio link monitoring error in theSeNB.

Example 112 includes the subject matter embodied by User Equipment (UE)adapted for communication with an evolved Node B (eNB), the UEcomprising: a transceiver arranged to transmit and receive communicationwith a Master eNB (MeNB) and a Secondary eNB (SeNB), and a processor,coupled to the transceiver, arranged to perform operations in connectionwith a connection to a MeNB and a connection to a SeNB: determine thatone of a connection to the MeNB and a connection to the SeNB has a RadioLink Failure, determine that the other one of the connection to the MeNBand the connection to the SeNB does not have a Radio Link Failure, andcommunicate to the one of the connection to the MeNB and the connectionto the SeNB to suspend at least one radio bearer used by the one of theconnection to the MeNB and the connection to the SeNB via the other oneof the connection to the MeNB and the connection to the SeNB.

In Example 113, the subject matter of Example 112 can optionally includewherein the one of the connection to the MeNB and the connection to theSeNB that has the Radio Link Failure is the connection to the MeNB andthe other one of the connection to the MeNB and the connection to theSeNB that does not have the Radio Link Failure is the connection to theSeNB, and wherein the MeNB is associated with a Primary Cell (PCell) andthe SeNB is associated with a Secondary Cell (SCell).

Each of these non-limiting examples can stand on its own, or can becombined in various permutations or combinations with one or more of theother examples.

The above detailed description includes references to the accompanyingdrawings, which form a part of the detailed description. The drawingsshow, by way of illustration, specific embodiments in which theinvention can be practiced. These embodiments are also referred toherein as “examples.” Such examples can include elements in addition tothose shown or described. However, the present inventors alsocontemplate examples in which only those elements shown or described areprovided. Moreover, the present inventors also contemplate examplesusing any combination or permutation of those elements shown ordescribed (or one or more aspects thereof), either with respect to aparticular example (or one or more aspects thereof), or with respect toother examples (or one or more aspects thereof) shown or describedherein.

In the event of inconsistent usages between this document and anydocuments so incorporated by reference, the usage in this documentcontrols.

In this document, the terms “a” or “an” are used, as is common in patentdocuments, to include one or more than one, independent of any otherinstances or usages of “at least one” or “one or more.” In thisdocument, the term “or” is used to refer to a nonexclusive or, such that“A or B” includes “A but not B,” “B but not A,” and “A and B,” unlessotherwise indicated. In this document, the terms “including” and “inwhich” are used as the plain-English equivalents of the respective terms“comprising” and “wherein.” Also, in the following claims, the terms“including” and “comprising” are open-ended, that is, a system, device,article, composition, formulation, or process that includes elements inaddition to those listed after such a term in a claim are still deemedto fall within the scope of that claim. Moreover, in the followingclaims, the terms “first,” “second,” and “third,” etc. are used merelyas labels, and are not intended to impose numerical requirements ontheir objects.

Method examples described herein can be machine or computer-implementedat least in part. Some examples can include a computer-readable mediumor machine-readable medium encoded with instructions operable toconfigure an electronic device to perform methods as described in theabove examples. An implementation of such methods can include code, suchas microcode, assembly language code, a higher-level language code, orthe like. Such code can include computer readable instructions forperforming various methods. The code may form portions of computerprogram products. Further, in an example, the code can be tangiblystored on one or more volatile, non-transitory, or non-volatile tangiblecomputer-readable media, such as during execution or at other times.Examples of these tangible computer-readable media can include, but arenot limited to, hard disks, removable magnetic disks, removable opticaldisks (e.g., compact disks and digital video disks), magnetic cassettes,memory cards or sticks, random access memories (RAMs), read onlymemories (ROMs), and the like.

The above description is intended to be illustrative, and notrestrictive. For example, the above-described examples (or one or moreaspects thereof) may be used in combination with each other. Otherembodiments can be used, such as by one of ordinary skill in the artupon reviewing the above description. The Abstract is provided to complywith 37 C.F.R. §1.72(b), to allow the reader to quickly ascertain thenature of the technical disclosure. It is submitted with theunderstanding that it will not be used to interpret or limit the scopeor meaning of the claims. Also, in the above Detailed Description,various features may be grouped together to streamline the disclosure.This should not be interpreted as intending that an unclaimed disclosedfeature is essential to any claim. Rather, inventive subject matter maylie in less than all features of a particular disclosed embodiment.Thus, the following claims are hereby incorporated into the DetailedDescription as examples or embodiments, with each claim standing on itsown as a separate embodiment, and it is contemplated that suchembodiments can be combined with each other in various combinations orpermutations. The scope of the invention should be determined withreference to the appended claims, along with the full scope ofequivalents to which such claims are entitled.

What is claimed is:
 1. An apparatus of a user equipment (UE), theapparatus comprising: a transceiver configured to transmit and receivecommunications with a Master evolved Node-B (MeNB) and a Secondaryevolved Node-B (SeNB) when the UE is configured with dual connectivity(DC); and processing circuitry coupled to the transceiver, theprocessing circuitry configured to detect a radio link failure (RLF) forthe SeNB, and upon detecting the RLF: encode for transmission to theMeNB, a radio resource control (RRC) indication that the connection withthe SeNB has experienced RLF; suspend radio bearers for the SeNB basedon the detected RLF for the SeNB; reset a media access control (MAC)layer associated with communications with the SeNB; and maintainconnection with radio bearers for the MeNB in a non-DC configuration. 2.The apparatus of claim 1, wherein the radio bearers for the SeNB includea data radio bearer (DRB).
 3. The apparatus of claim 1, wherein theradio bearers for the SeNB include a split DRB.
 4. The apparatus ofclaim 1, wherein the processing circuitry is configured to: determinethe connection with the SeNB has the RLF based on an expiration of anout-of-sync timer indicating lack of synchronization with the SeNB. 5.The apparatus of claim 1, wherein the processing circuitry is configuredto: determine the connection with the SeNB has the RLF based on a randomaccess problem indication received from a media access control (MAC)layer.
 6. The apparatus of claim 1, wherein the processing circuitry isconfigured to: decode an indication from a radio link control (RLC)layer of the SeNB that a maximum number of retransmissions has beenreached for a secondary cell group (SCG) of the SeNB; and determine aconnection with the SeNB has the RLF based on the decoded indication. 7.The apparatus of claim 1, wherein the processing circuitry is configuredto: refrain from initiating a radio resource control (RRC)re-establishment procedure between the UE and the SeNB while aconnection between the UE and the MeNB does not have a RLF.
 8. Theapparatus of claim 1, wherein the processing circuitry is configured to:upon detecting the RLF with the SeNB, apply one of a default physicalchannel configuration or a default semi-persistent schedulingconfiguration to maintain a connection with the MeNB.
 9. The apparatusof claim 1, wherein the processing circuitry is configured to: release aserving cell of the SeNB in response to a request from the MeNB upondetermining a connection to the SeNB has the RLF.
 10. The apparatus ofclaim 9, wherein the processing circuitry is configured to: reconfigureat least one radio bearer served by the SeNB in response to the requestfrom the MeNB.
 11. An apparatus of a first evolved Node-B (eNB), theapparatus comprising hardware processing circuitry, the processingcircuitry configured to: decode a radio resource control (RRC)indication from a user equipment (UE) that a connection between the UEand a second eNB has experienced a radio link failure (RLF), the UE in adual connectivity state with the first eNB and the second eNB; andencode a configuration message for transmission to the UE, to release asecondary cell group of the second eNB and suspend at least one radiobearer, the at least one radio bearer used prior to being suspended bythe second eNB to communicate with the UE.
 12. The apparatus of claim11, wherein the at least one radio bearer is one of a data radio bearer(DRB) or a split DRB.
 13. The apparatus of claim 11, wherein the firsteNB is a Master eNB (MeNB) and the second eNB is a Secondary eNB (SeNB),and wherein the MeNB is associated with a Primary Cell (PCell) and theSeNB is associated with a Secondary Cell (SCell).
 14. The apparatus ofclaim 13, wherein operations to suspend the at least one radio bearerused by the second eNB include operations to suspend all radio bearersused by the SeNB.
 15. An apparatus of a user equipment (UE), theapparatus comprising: processing circuitry, the processing circuitryconfigured to: detect a radio link failure (RLF) for a Secondary evolvedNode-B (SeNB), while the UE is in a dual connectivity (DC) state withthe SeNB and a Master evolved Node-B (MeNB); and upon detecting the RLF:encode for transmission to the MeNB, a radio resource control (RRC)indication that the connection with the SeNB has experienced RLF;suspend radio bearers for the SeNB, wherein the radio bearers for theSeNB include a data radio bearer (DRB) or a split DRB; reset a mediaaccess control (MAC) layer associated with communications with the SeNB;and maintain connection with radio bearers for the MeNB in a non-DCconfiguration.
 16. The apparatus of claim 15, wherein the MeNB isassociated with a Primary Cell (PCell) and the SeNB is associated with aSecondary Cell (SCell).
 17. The apparatus of claim 16, wherein theprocessing circuitry is further configured to: decode a Radio ResourceControl reconfiguration message from the MeNB to remove the SCell from aset of cells serving the UE.
 18. The apparatus of claim 15, wherein theprocessing circuitry is configured to: determine the connection with theSeNB has the RLF based on an expiration of an out-of-sync timerindicating lack of synchronization with the SeNB.
 19. The apparatus ofclaim 15, wherein the processing circuitry is configured to: determinethe connection with the SeNB has the RLF based on a random accessproblem indication received from the MAC layer associated withcommunications to the SeNB.
 20. The apparatus of claim 16, wherein theprocessing circuitry is configured to: decode an indication from a radiolink control (RLC) layer of the SeNB that a maximum number ofretransmissions has been reached for SCell of the SeNB; and determine aconnection with the SeNB has the RLF based on the decoded indication.21. A non-transitory computer readable storage device includinginstructions stored thereon, which when executed by one or moreprocessors of a User Equipment (UE), cause the UE to perform operationsto: detect a radio link failure (RLF) for a Secondary evolved Node-B(SeNB), while the UE is in a dual connectivity (DC) state with asecondary cell (SCell) of the SeNB and a primary cell (PCell) of aMaster evolved Node-B (MeNB); encode for transmission to the MeNB, aradio resource control (RRC) indication that the connection with theSeNB has experienced RLF; suspend radio bearers for the SeNB, whereinthe radio bearers for the SeNB include a data radio bearer (DRB) or asplit DRB; reset a media access control (MAC) layer associated withcommunications to the SeNB; and maintain connection with radio bearersfor the MeNB in a non-DC configuration.
 22. The non-transitory computerreadable storage device of claim 21, wherein the instructions furthercause the UE to perform operations to: decode a Radio Resource Controlreconfiguration message from the MeNB to remove the SCell from a set ofcells serving the UE.
 23. The non-transitory computer readable storagedevice of claim 21, wherein the instructions further cause the UE toperform operations to: determine the connection with the SeNB has theRLF based on an expiration of an out-of-sync timer indicating lack ofsynchronization with the SeNB.